home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Diamond Collection
/
The Diamond Collection (Software Vault)(Digital Impact).ISO
/
cdr37
/
qlogin06.zip
/
QLOGIN.DOC
< prev
next >
Wrap
Text File
|
1994-10-16
|
8KB
|
170 lines
┌─────────────────────────────────────────────────────────────────────────────┐
│ ┌──────┐ ┌─┐ ┌──────┐ ┌──────┐ ┌───┐ ┌───┐ ┌─┐ │
│ │ ┌──┐ │ │ │ │ ┌──┐ │ │ ┌────┘ └┐ ┌┘ │ └┐ │ │ │
│ │ │ │ │ │ │ │ │ │ │ │ │ ┌──┐ │ │ │ ├┐ └┐│ │ │
│ │ │ │ │ │ │ │ │ │ │ │ │ └┐ │ │ │ │ │└┐ └┤ │ │
│ │ └──┘ │ │ └──┐ │ └──┘ │ │ └──┘ │ ┌┘ └┐ │ │ └┐ │ │
│ └───┐ ┌┘ └────┘ └──────┘ └──────┘ └───┘ └─┘ └───┘v0.60ß │
│ ┴─┴ The ≡FAST≡ Login Utility for ProBoard 2.x │
│ Another Fine HomeGrown Pex. (C)1994 G.Smith │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
What is QLOGIN?
===============
QLOGIN is a utility to allow your users to bypass one-liners, news
screens etc and go straight to the main menu. It is written in such a
way that you can make all of your most used options available from the
QLOGIN menu.
Installation
=============
1. Edit the QLOGIN.INI file to configure your QLOGIN menu. The QLOGIN.INI
file is well commented, so just follow the instructions within that
file. Once you have finished editing, copy the QLOGIN.INI file into your
\PROBOARD\PEX directory. QLOGIN will check your system path, and expect
to find QLOGIN.INI in a directory called PEX, just below your main
proboard directory.
2. Edit QLOGIN.ANS/ASC to match the configuration settings in
QLOGIN.INI. QLOGIN will expect to find the QLOGIN.ANS/QLOGIN.ASC files
in the TEXTFILES directory which is set in PROCFG - Options|Paths.
Take not of the position (Column ,Row) of your selection prompt. You need
these co-ordinates to correctly set the cursor position on the menu
screen. If you intend to have a separate sysop menu, edit QSYSOP.ANS/ASC
to match the additional 'sysop only' configuration settings in
QLOGIN.INI
3. Rename QLOGIN.PEX to WELCOME1.PEX and place it in your PEX directory.
4. If you have any files such as NEWS.* that you wish only to be
shown/executed during a 'Normal' login, rename them to something else
and set them up in the Action options in QLOGIN.INI.
eg.. rename NEWS.* to DBNEWS.* / rename welcome2.pex to qlogin2.pex
Configuration Keywords
======================
SysopLevel - The inclusion of this setting causes QLOGIN to look for
(and expect to find) an additional menu screen called
QSYSOP.A?? in Proboard's textfiles directory. This
additional screen will only be shown to those with a
security level equal to or greater that the SysopLevel.
eg. SysopLevel = 32000
CursorX
CursorY - These settings determine the position of the cursor on the
menu (ans/avt) screen. When designing your screen, take
note of the position of your 'Choice:' prompt. CursorX is
the column number, and CursorY is the line number.
eg. CursorX = 5 <- 5 characters in from left of screen
CursorY = 20 <- 20 lines down from top of screen
MenuOptionCount
ActionCount - These settings reflect the number of menuOptions and
Actions you have set. Be very careful with these. If
you have 5 menu options, and the MenuOptionCount is
set to 4, the 5th option will _not_ work. This setting
was added to enhance speed. Rather than searching for
20 menuOptions every time, QLOGIN will only look for
the number in this setting.
eg. MenuOptionCount = 9
ActionCount = 5
MenuOption(n) - You may have up to 20 menu options. These menu options
should be numbered in sequence ie MenuOption1,
MenuOption2 .. MenuOption20. If you only have 5 menu
options, then just use MenuOption1 .. MenuOption5.
This setting is the type of menu function. It takes a
menu command number as a parameter. The menu command
numbers are the same as those in PROCFG|Menu Editor.
eg. MenuOption1 = 37 <- Menu option number (same as in PROCFG)
This one is '37 - Show New Files'
MenuOption(n)_Key - This is the hotkey for a specific menu function.
eg. MenuOption1_Key = -N <- This is the 'hotkey' for this option (N)
MUST be preceded by a '-' minus sign.
MenuOption(n)_Data - This is the accompanying data for a menu function.
The format/options are the same as in PROCFG|Menu
Editor.
eg. MenuOption1_Data = * -C <- additional data for this menu option.
Same format as menu data field in PROCFG
MenuOption(n)_Level - This setting determines the minimum security level
required in order to access this menu option.
eg. MenuOption1_Level = 5 <- Min. Security level required in
order to use this feature. (same
levels as in PROCFG). If you do not
use the MenuOption(n)_Level settings,
they default to 0.
Action(n) - This setting works the same as the MenuOption(n) setting.
The parameter is a menu function number. The actions are
executed if a user selects the normal login. You may define
up to 10 actions, numbered sequentially from Action1 ..
Action10.
Action(n)_Data - This is the accompanying data for the specific action
such as the name of a *.ans/*.asc file in the case of
an Action(n) = 5 (Show *.ANS/*.ASC File), or the name
of a pex file in the case of Action(n) = 60.
eg. Action1 = 5
Action1_Data = DBNEWS <- *.ANS/*.ASC File name
Action(n)_Level - This is the minimum security level required for the
user to 'see' this action when he chooses a normal
login.
Comments
========
As this is a beta, I am particularly interested in getting feedback
regarding any problems you may have, or any suggestions for
improvements. I am aware that there are several menu options that won't
work in the MenuOption section of QLOGIN. I'm not sure if this is a
program 'bug' as such, or simply not possible at that stage of the login
sequence. As an example, it is not possible to execute a 'Goto Menu' or
'Gosub Menu' function. I have not yet tested all menu functions, but
will compile a list of available options/numbers at a later stage.
Copyright Notice
----------------
QLOGIN is 'donorware'. You are under no obligation to pay for this
program, but are welcome to send a donation of $US10 to keep the
author's spirits up..:) Feedback and any donations will help to ensure
the continued development of QLOGIN. I have several additional features
planned and will be very receptive to any other suggestions.
The author will take no responsibility for any damage that may be caused
by the use, proper or improper, of this program. The only guarantee given
is that it will use some hard disk space.
Contacting the Author
---------------------
BBS: DataBus/2 Fidonet: 3:637/103 AceNet: 133:666/15
Ph. +61-53-362-775 TriNet : 42:8699/51
24hrs V.FC
Internet: gsmith@nova.ballarat.edu.au
Snail Mail: Gary Smith,
P.O. Box 192,
Sebastopol,
Vic. 3356
Australia